|
|
|
|
|
|
|
5. Using the guidelines from Day 6, proceed to create your ActiveX component by choosing File|Make from the menu. |
|
|
|
|
|
|
|
|
To create a concrete component that implements the interface classes in your abstract component, follow these steps: |
|
|
|
|
|
|
|
|
1. Open a new ActiveX project. |
|
|
|
|
|
|
|
|
2. Choose Project References from the menu to add the abstract component you created to your new project. |
|
|
|
|
|
|
|
|
3. Add one or more classes to your project. If you design one class to implement every interface in the abstract component, you only need to add one class. |
|
|
|
|
|
|
|
|
4. In the General Declarations section of each class you just added, enter Implements <abstract component>.<name of abstract interface>, where <abstract component> is the abstract component you created earlier, and <name of abstract interface> is the name of the interface class in your abstract component you wish to implement. If your class will implement more than one interface, then you will need to repeat this step for each one. |
|
|
|
|
|
|
|
|
5. Implement each interface method for each interface object in each class's object list. That is, add some code to each interface method. Debug your code thoroughly. |
|
|
|
|
|
|
|
|
6. In the NewBasicPersonalChecking class's object list, look for the AbstractCheckingProduct interface object. If you're able to see it, then you've successfully created an abstract component. Move the code from the class methods to the interface methods of the AbstractCheckingProduct interface object. |
|
|
|
|
|
|
|
|
7. Using the guidelines from Day 6, proceed to create your ActiveX component by choosing File|Make from the menu. |
|
|
|
|
|
|
|
|
To create subsystems in a quality fashion, it is also important to control the versions of subsystems. As mentioned on Day 8, Versioning and Debugging, a good way to manage the versions of a subsystem in SourceSafe for relatively large projects is to allocate an independent source project to it, inaccessible to external, nonowner users. |
|
|
|
|
|
|
|
|
The Object Interaction Structure of a Subsystem |
|
|
|
|
|
|
|
|
The meaningful substance of subsystems is represented by the interactions between objects contained within them. The object interactions are realized based on the kinds of objects in the subsystems. Based on the Objectory Process Extension of the UML, such object kinds for a subsystem might include |
|
|
|
|
|